Method and system for platform attribution using digitized tokens

ABSTRACT

A method for identifying a plurality of related computing devices related to a transaction account includes: storing token profiles, each including data related to a payment token including a digital token number, associated transaction account number, computing device identifier, and computing device data; receiving a transaction data entry related to an electronic transaction including transaction data and one of: a specific transaction account number or an associated specific digital token number; identifying a plurality of related token profiles where the included associated transaction account number corresponds to the specific transaction account number; identifying a third party entity associated with at least one identified token profile; and electronically transmitting the transaction data included in the transaction data entry and at least one of: the computing device identifier and computing device data included in each of the identified plurality of related token profiles to the third party entity.

FIELD

The present disclosure relates to identifying a group of relatedcomputing devices via the use of digitized tokens for platformattribution, specifically the identification of computing devices thatare associated with digitized tokens that are each associated with acommon account such as may be used in the attribution of advertisementsand other content to the respective computing devices.

BACKGROUND

As technology increases, the number of computing devices with which theaverage consumer interacts also increases. In the past, a consumer mayhave possessed a home desktop computer that they used for all of theirInternet browsing and e-commerce needs. In such instances, anadvertisement that was displayed to the consumer prior to the consumermaking a related purchase might get credit for attribution of thepurchase because of the commonality of the identification of thecommunication device, via browser-based cookies stored in the desktopcomputer or other known identification mechanisms. However, astechnology has increased, the same consumer may now possess multiplecomputer platforms such as their home desktop computer, as well as alaptop computer, a tablet computer, and a smart phone, for instance,each possibly presenting a different set of communication channels. Theconsumer may be exposed to an advertisement on each of the platformsbefore finally making a purchase using one of the platforms or via anin-person payment transaction.

In many systems, the purchase may be attributed to the platform withwhich the consumer made their purchase. However, such systems mayneglect to consider the other platforms used by the consumer on whichthey were exposed to an advertisement or content related to thepurchase. In the case of an in-person transaction, no platform mayreceive attribution for the purchase as traditional attribution systemsand advertising agencies are unable to identify in-person transactions,let alone further identify a computing device used by the consumer priorto the transaction.

Thus, there is a need for a technical solution to enable the attributionof individual purchases to multiple computing devices. Identification ofa transaction account associated with a computing device may enable theattribution of a computing device (e.g., that has received a relatedadvertisement) to a purchase. However, in many instances, computingdevices may receive digitized tokens for use in payment transactions inplace of traditional account credentials. As such, computing devices maybe associated with digitized tokens and not directly associated with atransaction account. Thus, many computing systems may be unable toidentify a transaction account associated with a computing device,instead being limited to identifying the associated digitized token.Therefore, there is also a need for a technical solution where a systemthat is configured to manage the use of digitized tokens is furtherconfigured to identify related computing devices based on associateddigitized tokens and transaction account data for use in platformattribution.

Some methods have been developed for the use of a single identifier thatis associated with a transaction account that is different from thetransaction account number, which may be used as an identifier fortransactions using the real transaction account number as well as anydigital tokens associated with that account. For example, some paymentcard standards suggest the use of a payment account reference (PAR), aunique identifier associated with a transaction account that is storedin an additional data element conveyed any time the real transactionaccount number or any associated digital token is used. However, the useof an additional reference number in transactions themselves may requiremodification to all existing points of sale, payment networks, financialinstitutions, and merchant systems. In addition, while this informationmay be used during the processing of transactions, it may be unavailableto advertisers and other entities, which may be able to identify that apurchase is made using a device, but may be prohibited from accessingany payment information from that device. Thus, there is a need for atechnical solution for enhanced attribution of computing devices thatutilizes information identifying the devices themselves, which can beassociated together without modification to legacy transaction systems.

SUMMARY

The present disclosure provides a description of systems and methods foridentifying a plurality of related computing devices related to atransaction account.

A method for identifying a plurality of related computing devicesrelated to a transaction account includes: storing, in a token profiledatabase of a processing server, a plurality of token profiles, whereineach token profile includes a structured data set related to a paymenttoken including at least a digital token number, an associatedtransaction account number, a computing device identifier, and computingdevice data; storing, in a transaction database of the processingserver, a plurality of transaction data entries, wherein eachtransaction data entry includes a structured data set related to anelectronic transaction including at least a specific digital tokennumber or specific transaction account number used in funding therelated electronic transaction and transaction data; receiving, by areceiving device of the processing server, a data signal superimposedwith a related device request electronically transmitted from a thirdparty entity, wherein the related device request includes at least aspecific computing device identifier; executing, by a querying module ofthe processing server, a query on the token profile database to identifya specific token profile where the included computing device identifiercorresponds to the specific computing device identifier; executing, bythe querying module of the processing server, a query on the tokenprofile database to identify a plurality of related token profiles wherethe included associated transaction account number corresponds to theassociated transaction account number included in the identifiedspecific token profile; executing, by the querying module of theprocessing server, a query on the transaction database to identify aspecific transaction data entry where the included specific digitaltoken number or specific transaction account number corresponds to adigital token number or associated transaction account number includedin at least one of the identified plurality of related token profiles orthe identified specific token profile; and electronically transmitting,by a transmitting device of the processing server, a data signal to thethird party entity superimposed with at least the transaction dataincluded in the identified specific transaction data entry and at leastone of: the computing device identifier and computing device dataincluded in each of the identified plurality of related token profiles.

Another method for identifying a plurality of related computing devicesrelated to a transaction account includes: storing, in a token profiledatabase of a processing server, a plurality of token profiles, whereineach token profile includes a structured data set related to a paymenttoken including at least a digital token number, an associatedtransaction account number, a computing device identifier, and computingdevice data; receiving, by a receiving device of the processing server,a transaction data entry related to an electronic transaction, whereinthe transaction data entry includes at least transaction data and oneof: a specific transaction account number or a specific digital tokennumber associated with a specific transaction account number; executing,by a querying module of the processing server, a query on the tokenprofile database to identify a plurality of related token profiles wherethe included associated transaction account number corresponds to thespecific transaction account number; identifying, by a dataidentification module of the processing server, a third party entityassociated with at least one token profile included in the identifiedplurality of related token profiles; and electronically transmitting, bya transmitting device of the processing server, a data signal to theidentified third party entity superimposed with at least the transactiondata included in the transaction data entry and at least one of: thecomputing device identifier and computing device data included in eachof the identified plurality of related token profiles.

A system for identifying a plurality of related computing devicesrelated to a transaction account includes: a token profile database of aprocessing server configured to store a plurality of token profiles,wherein each token profile includes a structured data set related to apayment token including at least a digital token number, an associatedtransaction account number, a computing device identifier, and computingdevice data; a transaction database of the processing server configuredto store a plurality of transaction data entries, wherein eachtransaction data entry includes a structured data set related to anelectronic transaction including at least a specific digital tokennumber or specific transaction account number used in funding therelated electronic transaction and transaction data; a receiving deviceof the processing server configured to receive a data signalsuperimposed with a related device request electronically transmittedfrom a third party entity, wherein the related device request includesat least a specific computing device identifier; a querying module ofthe processing server configured to execute a query on the token profiledatabase to identify a specific token profile where the includedcomputing device identifier corresponds to the specific deviceidentifier, a query on the token profile database to identify aplurality of related token profiles where the included associatedtransaction account number corresponds to the associated transactionaccount number included in the identified specific token profile, and aquery on the transaction database to identify a specific transactiondata entry where the included specific digital token number or specifictransaction account number corresponds to a digital token number orassociated transaction account number included in at least one of theidentified plurality of related token profiles or the identifiedspecific token profile; and a transmitting device of the processingserver configured to electronically transmit a data signal to the thirdparty entity superimposed with at least the transaction data included inthe identified specific transaction data entry and at least one of: thecomputing device identifier and computing device data included in eachof the identified plurality of related token profiles.

Another system for identifying a plurality of related computing devicesrelated to a transaction account includes: A token profile database of aprocessing server configured to store a plurality of token profiles,wherein each token profile includes a structured data set related to apayment token including at least a digital token number, an associatedtransaction account number, a computing device identifier, and computingdevice data; a receiving device of the processing server configured toreceive a transaction data entry related to an electronic transaction,wherein the transaction data entry includes at least transaction dataand one of: a specific transaction account number or a specific digitaltoken number associated with a specific transaction account number; aquerying module of the processing server configured to execute a queryon the token profile database to identify a plurality of related tokenprofiles where the included associated transaction account numbercorresponds to the specific transaction account number; a dataidentification module of the processing server configured to identify athird party entity associated with at least one token profile includedin the identified plurality of related token profiles; and atransmitting device of the processing server configured toelectronically transmit a data signal to the identified third partyentity superimposed with at least the transaction data included in thetransaction data entry and at least one of: the computing deviceidentifier and computing device data included in each of the identifiedplurality of related token profiles.

BRIEF DESCRIPTION OF THE DRAWING FIGURES

The scope of the present disclosure is best understood from thefollowing detailed description of exemplary embodiments when read inconjunction with the accompanying drawings. Included in the drawings arethe following figures:

FIG. 1 is a block diagram illustrating a high level system architecturefor identifying related computing devices related to a transactionaccount for platform attribution in accordance with exemplaryembodiments.

FIG. 2 is a block diagram illustrating the processing server of FIG. 1for the identification of related computing devices in accordance withexemplary embodiments.

FIG. 3 is a flow diagram illustrating a process for identifyingcomputing devices and transaction data related to a provided computingdevice via digitized tokens and corresponding transaction account datain accordance with exemplary embodiments.

FIG. 4 is a flow diagram illustrating a process for identifyingcomputing devices related to a payment transaction via digitized tokensand corresponding transaction account data in accordance with exemplaryembodiments.

FIGS. 5 and 6 are flow charts illustrating exemplary methods foridentifying a plurality of related computing devices related to atransaction account in accordance with exemplary embodiments.

FIG. 7 is a flow diagram illustrating the processing of a paymenttransaction in accordance with exemplary embodiments.

FIG. 8 is a block diagram illustrating a computer system architecture inaccordance with exemplary embodiments.

Further areas of applicability of the present disclosure will becomeapparent from the detailed description provided hereinafter. It shouldbe understood that the detailed description of exemplary embodiments areintended for illustration purposes only and are, therefore, not intendedto necessarily limit the scope of the disclosure.

DETAILED DESCRIPTION

Glossary of Terms

Payment Network—A system or network used for the transfer of money viathe use of cash-substitutes. Payment networks may use a variety ofdifferent protocols and procedures in order to process the transfer ofmoney for various types of transactions. Transactions that may beperformed via a payment network may include product or servicepurchases, credit purchases, debit transactions, fund transfers, accountwithdrawals, etc. Payment networks may be configured to performtransactions via cash-substitutes, which may include payment cards,letters of credit, checks, transaction accounts, etc. Examples ofnetworks or systems configured to perform as payment networks includethose operated by MasterCard®, VISA®, Discover®, American Express®,PayPal®, etc. Use of the term “payment network” herein may refer to boththe payment network as an entity, and the physical payment network, suchas the equipment, hardware, and software comprising the payment network.

Payment Rails—Infrastructure associated with a payment network used inthe processing of payment transactions and the communication oftransaction messages and other similar data between the payment networkand other entities interconnected with the payment network. The paymentrails may be comprised of the hardware used to establish the paymentnetwork and the interconnections between the payment network and otherassociated entities, such as financial institutions, gateway processors,etc. In some instances, payment rails may also be affected by software,such as via special programming of the communication hardware anddevices that comprise the payment rails. For example, the payment railsmay include specifically configured computing devices that are speciallyconfigured for the routing of transaction messages, which may bespecially formatted data messages that are electronically transmittedvia the payment rails, as discussed in more detail below.

Payment Card—A card or data associated with a transaction account thatmay be provided to a merchant in order to fund a financial transactionvia the associated transaction account. Payment cards may include creditcards, debit cards, charge cards, stored-value cards, prepaid cards,fleet cards, virtual payment numbers, virtual card numbers, controlledpayment numbers, etc. A payment card may be a physical card that may beprovided to a merchant, or may be data representing the associatedtransaction account (e.g., as stored in a communication device, such asa smart phone or computer). For example, in some instances, dataincluding a payment account number may be considered a payment card forthe processing of a transaction funded by the associated transactionaccount. In some instances, a check may be considered a payment cardwhere applicable.

System for Identification of Related Computing Devices for PlatformAttribution

FIG. 1 illustrates a system 100 for the identification of relatedcomputing devices that are each related to a transaction account for usein platform attribution of advertisements and other content.

The system 100 may include a processing server 102. The processingserver 102, discussed in more detail below, may be configured toidentify a plurality of computing devices that are each related to asingle transaction account and the identification of transaction dataassociated therewith, which may be used in platform attribution. Thatis, a processor or processors in the processing server 102, including atleast a querying module 214, a data identification module 216, ageneration module 218 and a transaction processing module 220, as shownin FIG. 2, is specifically programmed through executable code touniquely configure a logic array in the processor to have a complexcombination of logic operations to carry out the functions disclosedherein, which a general purpose computer is incapable of performingwithout this specific, unconventional programming, in one example. Inthe system 100, an advertising agency 104 or other content provider mayelectronically distribute content, such as an advertisement for thepurchase of goods or services, a coupon, deal, or discount for thepurchase of goods or services, or other suitable content to a pluralityof different computing devices 106 via a communication network 108.

Each computing device 106 may be any type of computing device suitablefor the receipt and display of content to a user, such as a desktopcomputer, laptop computer, notebook computer, tablet computer, cellularphone, smart phone, smart television, smart watch, wearable computingdevice, implantable computing device, etc. The communication network 108may be any type of communication network suitable for performing thefunctions discussed herein, such as a cellular communication network,the Internet, a local area network, a radio frequency network, etc. Insome instances, a plurality of different communication networks may beused in performing the functions discussed herein, such as the use ofthe Internet and a cellular communication network for electroniccommunications between the advertising agency 104 and the computingdevices 106.

In the system 100, a consumer 110 may possess a plurality of differentcomputing devices 106, which may be used in the receipt and browsing ofcontent, such as advertisements or other content submitted by theadvertising agency 104. The consumer 110 may use the computing device106 and may be exposed to an advertisement provided by the advertisingagency 104 for a particular product (e.g., a good or service). Theconsumer 110 may eventually make a decision to purchase the advertisedproduct.

To affect the purchase, the consumer 110 may use a payment card 112 inthe funding of a payment transaction for the advertised product from amerchant 114. In some embodiments, the payment card 112 may be aphysical payment card provided to a point of sale device associated withthe merchant 114, from which payment credentials are read (e.g., viamagnetic stripe, near field communication, an integrated circuit, etc.).In other embodiments, the payment card 112 may be a virtual paymentcard, where associated payment credentials may be communicated to thecomputing systems of the merchant 114 electronically, perhaps through apoint of sale or point device of interaction such as a check-out pagedisplayed in a browser. For example, the consumer 110 may use acomputing device 106 to convey payment details for the paymenttransaction. The computing device 106 may be configured toelectronically transmit the payment details via near fieldcommunication, radio frequency, transmission over a network such as theInternet, or other suitable type of communication, the computing device106 may display a machine-readable code encoded with the payment detailsfor reading and decoding by the computing systems of the merchant 114,the computing device 106 may initiate the transmission of paymentdetails to the computing systems of the merchant 114 via a third party,etc. Suitable methods for providing payment credentials to a merchant114 computing system will be apparent to persons having skill in therelevant art.

In some embodiments, a computing device 106 may be provisioned with adigitized payment token in place of a traditional transaction accountnumber for use in funding payment transactions. For example, theconsumer 110 may register a computing device 106 with a tokendistribution platform, which may receive account credentials andauthentication information from the consumer 110 and, once the consumeris authenticated as being authorized to request a digitized token forthe transaction account, may generate and distribute a digitized paymenttoken to the computing device 106. Methods for provisioning digitizedpayment tokens to computing devices 106 will be apparent to personshaving skill in the relevant art. A payment token may be a digitizedtoken that is conveyed to a merchant 114 computing system in place of atraditional transaction account number. The payment token may be used inthe processing of the payment transaction where the related transactionaccount may be identified and the transaction processed accordinglyusing traditional methods. Payment tokens may be associated with asingle computing device 106 such that if a different computing deviceattempts to use the payment token for funding of a payment transaction,the payment transaction may be denied accordingly. In such instances,payment tokens may be beneficial as the token details may be unusableoutside of the specifically associated computing device 106.

The computing systems of the merchant 114 may be configured toelectronically transmit transaction data, including the payment detailsprovided by the consumer 110 (e.g., including a transaction accountnumber or token details from the payment card 112 or a computing device106), to a payment network 116 for processing using the payment rails.In some instances, the transaction data may be transmitted to one ormore intermediate entities, such as an acquiring financial institution,gateway processor, etc., for forwarding to the payment network 116 in atransaction message using the payment rails. A transaction message maybe a specially formatted data message that is formatted based on one ormore standards governing the exchange of financial transaction messages,such as the International Organization for Standardization's ISO 8583message. The transaction message may include a plurality of dataelements configured to store data as set forth in the associatedstandards, which may include at least one data element configured tostore a primary account number. The data element configured to store aprimary account number may store the transaction account number or atoken number associated with a digitized token, for use in funding therelated payment transaction. A transaction message may also includeadditional data, such as a message type indicator indicative of a typeof the transaction message. The payment network 116 may receive thetransaction message and may process the payment transaction accordinglyusing traditional methods and systems, where, in instances where adigitized payment token is used, the transaction is processed using thetransaction account associated with the digitized payment token. Theexchange of transaction messages and processing of payment transactionsis discussed in more detail below with respect to the process 700illustrated in FIG. 7.

In the system 100, the processing server 102 may be configured to storetoken profiles associated with digitized payment tokens. Each tokenprofile may include a digitized payment token or information inidentification thereof (e.g., a digital token number), the associatedtransaction account number, and data associated with the computingdevice 106 to which the respective digitized payment token wasdistributed. The computing device data may include a device identifier,such as an identification number, registration number, serial number,media access control address, internet protocol address, username,e-mail address, phone number, etc., as well as additional dataassociated with the computing device 106, such as a make, model,manufacturer, form factor, architecture, type, geographic location, etc.In some embodiments, the processing server 102 may receive the data fortoken profiles from a token distribution platform configured toprovision tokens to computing devices 106. In some instances, theprocessing server 102 may be a token distribution platform or may bepart of a computing system configured to operate as a token distributionplatform, and may identify the data for token profiles as a result offunctions performed in connection therewith. In other embodiments, theprocessing server 102 may be configured to receive token profile datafrom a payment network 116 or other entity associated with such data,such as a financial institution (e.g., an issuing bank) associated withthe transaction account to which a digitized payment token corresponds.

The processing server 102 may also be configured to store transactiondata for payment transactions involving the digitized payment tokens andcorresponding transaction accounts. In some embodiments, the paymentnetwork 116 may electronically transmit transaction data to theprocessing server 102 via the payment rails or a communication network108. In some instances, the payment network 116 may transmit transactionmessages to the processing server 102. In other instances, the paymentnetwork 116 may transmit transaction data parsed from the transactionmessages in a separate data signal. The transaction data may include atleast a digital token number or transaction account number used to fundthe related payment transaction, and may also include additional datasuitable for performing the functions discussed herein, such as consumerdata, merchant data, point of sale data, product data, reward data,loyalty data, offer data, issuer data, acquirer data, etc. In someembodiments, the processing server 102 may be a part of the paymentnetwork 116 and may receive transaction data via internal communicationand processing. In other embodiments, the processing server 102 may beconfigured to receive transaction messages from the payment network 116for use in mapping digital token numbers to transaction account numbers,such as in instances where the processing server 102 may be part of atoken distribution and processing platform.

The processing server 102 may be configured to identify relatedcomputing devices 106 using the token profile data. In one embodiment,an advertising agency 104 may electronically transmit a data signal tothe processing server 102 using the communication network 108 that issuperimposed with a device identifier associated with a computing device106, such as a computing device 106 that the advertising agency 104knows was exposed to an advertisement or other distributed content. Theprocessing server 102 may receive the device identifier and may identifya token profile related to a digitized payment token distributed to thatcomputing device 106 that includes the device identifier. The processingserver 102 may then identify every token profile related to that tokenprofile based on the inclusion of the same transaction account numberincluded. The related token profiles may thus correspond to computingdevices 106 that include tokens that are all associated with the sametransaction account.

The processing server 102 may be configured to provide computing devicedata included in each of the identified related token profiles to theadvertising agency 104 via the electronic transmission of a data signalsuperimposed therewith using the communication network 108. Theadvertising agency 104 may then receive the data, which may include dataassociated with each of the computing devices 106 associated with atransaction account (e.g., and therefore a consumer 110), which may beused by the advertising agency 104 in attribution. In some instances,the processing server 102 may also identify transaction datacorresponding to one or more payment transactions involving thetransaction account, such as by identifying transaction data for apayment transaction that includes the transaction account number or oneof the digital token numbers included in the related token profiles. Insome embodiments, the processing server 102 may receive transaction datafor a payment transaction, which may then be used by the processingserver 102 in the identification of the related token profiles, such asby identifying a token profile that includes a digital token numberincluded in the received transaction data and the related token profilesor by identifying all token profiles that include a transaction accountnumber included in the received transaction data. In such an instance,the processing server 102 may provide the computing device data to theadvertising agency 104 without the receipt of a request from theadvertising agency 104. In such instances, the processing server 102 mayidentify the advertising agency based on data stored in one of theidentified token profiles. The transaction data may be electronicallytransmitted to the advertising agency 104 using the communicationnetwork 108 along with the computing device data, which may then be usedby the advertising agency 104 in attribution.

For example, the advertising agency 104 may distribute an advertisementfor a toaster to a wide selection to computing devices 106. A consumer110 may be exposed to the advertisement on three different computingdevices 106, and may eventually decide to purchase the toaster. Theconsumer 110 may go to a physical storefront of a merchant 114 andpresent a physical payment card 112 to purchase the toaster. Thetransaction may be processed by the payment network 116 and transactiondata provided to the processing server 102, and the consumer 110 mayreceive their new toaster once the transaction is finalized. Intraditional systems, the advertising agency 104 would be unaware of theconsumer's purchase due to a physical payment card 112 being used. Ininstances where the consumer 110 may use one of the three computingdevices 106 for the purchase, the advertising agency 104 would attributethe purchase to that one computing device 106, being unaware that theconsumer 110 received the advertisement on two additional devices.

In the system 100, the advertising agency 104 may receive dataidentifying each of the three computing devices 106 associated with theconsumer 110, as well as transaction data for the purchase, even ininstances where a physical payment card 112 is used. The advertisingagency 104 may be able to use the combined data to identify attributionfor the purchase. For instance, in a first example, the advertisingagency 104 may identify that the consumer 110 was exposed to theadvertisement three separate times (e.g., once on each computing device106) and may attribute the purchase to each of the three platforms usedto deliver the advertisement. In a second example, the transactiondetails may indicate that the transaction was conducted before theconsumer 110 was shown the advertisement on their third computing device106, which may thus result in attribution to only the first twoplatforms. In some instances, the advertising agency 104 may also beable to use the computing device data for calculating metrics regardingadvertisements, platforms, and purchasing. For example, the advertisingagency 104 may identify more accurate data regarding the number ofexposures to an advertisement before purchase, the length of timebetween first exposure and purchase, the effectiveness of some platformsover others for purchases, etc. In some embodiments, the metrics may becalculated by the processing server 102, such as based on informationassociated with the exposure of the advertisement. In such anembodiment, the processing server 102 may provide the metrics to theadvertising agency 104 along with the identified computing device data.

Processing Server

FIG. 2 illustrates an embodiment of the processing server 102 of thesystem 100. It will be apparent to persons having skill in the relevantart that the embodiment of the processing server 102 illustrated in FIG.2 is provided as illustration only and may not be exhaustive to allpossible configurations of the processing server 102 suitable forperforming the functions as discussed herein. For example, the computersystem 800 illustrated in FIG. 8 and discussed in more detail below maybe a suitable configuration of the processing server 102.

The processing server 102 may include a receiving device 202. Thereceiving device 202 may be configured to receive data over one or morenetworks via one or more network protocols. In some embodiments, thereceiving device 202 may be configured to receive data over the paymentrails, such as using specially configured infrastructure associated withpayment networks 116 for the transmission of transaction messages thatinclude sensitive financial data and information. In some instances, thereceiving device 202 may also be configured to receive data fromadvertising agencies 104, computing devices 106, merchants 114, paymentnetworks 116, and other entities via alternative networks, such as theInternet. In some embodiments, the receiving device 202 may be comprisedof multiple devices, such as different receiving devices for receivingdata over different networks, such as a first receiving device forreceiving data over payment rails and a second receiving device forreceiving data over the Internet. The receiving device 202 may receiveelectronically data signals that are transmitted, where data may besuperimposed on the data signal and decoded, parsed, read, or otherwiseobtained via receipt of the data signal by the receiving device 202. Insome instances, the receiving device 202 may include a parsing modulefor parsing the received data signal to obtain the data superimposedthereon. For example, the receiving device 202 may include a parserprogram configured to receive and transform the received data signalinto usable input for the functions performed by the processing deviceto carry out the methods and systems described herein.

The receiving device 202 may be configured to receive data signalselectronically transmitted by advertising agencies 104, which may besuperimposed with data requests. The data requests may include specificcomputing device identifiers, associated with a computing device 106 forwhich the advertising agency 104 wants related device and/or transactiondata for use in attribution. In some instances, the data request mayidentify transaction data, such as a product for which transaction andrelated device data is identified. The receiving device 202 may alsoreceive data signals from the advertising agencies 104 superimposed withdevice identifiers for use in identification of the advertising agency104, such as in instances when transaction data is received related to acomputing device to which the advertising agency 104 is associated. Thereceiving device 202 may also be configured to receive transaction data,such as via transaction messages or other data signals electronicallytransmitted by the payment network 116 using the payment rails r acommunication network 108. The receiving device 202 may also beconfigured to receive token and computing device data, such as from thepayment network 116, computing devices 106, financial institutions,token profile distribution platforms, and other suitable entities.

The processing server 102 may also include a communication module 204.The communication module 204 may be configured to transmit data betweenmodules, engines, databases, memories, and other components of theprocessing server 102 for use in performing the functions discussedherein. The communication module 204 may be comprised of one or morecommunication types and utilize various communication methods forcommunications within a computing device. For example, the communicationmodule 204 may be comprised of a bus, contact pin connectors, wires,etc. In some embodiments, the communication module 204 may also beconfigured to communicate between internal components of the processingserver 102 and external components of the processing server 102, such asexternally connected databases, display devices, input devices, etc. Theprocessing server 102 may also include a processing device. Theprocessing device may be configured to perform the functions of theprocessing server 102 discussed herein as will be apparent to personshaving skill in the relevant art. In some embodiments, the processingdevice may include and/or be comprised of a plurality of engines and/ormodules specially configured to perform one or more functions of theprocessing device, such as a querying module 214, data identificationmodule 216, generation module 218, transaction processing module 220,etc. As used herein, the term “module” may be software or hardwareparticularly programmed to receive an input, perform one or moreprocesses using the input, and provide an output. The input, output, andprocesses performed by various modules will be apparent to one skilledin the art based upon the present disclosure.

The processing server 102 may include a token profile database 206. Thetoken profile database 206 may be configured to store a plurality oftoken profiles 208 using a suitable data storage format and schema. Thetoken profile database 206 may be a relational database that utilizesstructured query language for the storage, identification, modifying,updating, accessing, etc. of structured data sets stored therein. Eachtoken profile 208 may be a structured data set configured to store dataassociated with a digitized payment token, which may include at least adigital token number, a transaction account number for the transactionaccount associated with the digitized payment token, and a computingdevice identifier and additional computing device data associated with acomputing device 106 to which the digitized payment token wasprovisioned.

The processing server 102 may also include a transaction database 210.The transaction database 210 may be configured to store a plurality oftransaction data entries 212 using a suitable data storage format andschema. The transaction database 210 may be a relational database thatutilizes structured query language for the storage, identification,modifying, updating, accessing, etc. of structured data sets storedtherein. Each transaction data entry 212 may be a structured data setconfigured to store data related to a payment transaction, including atleast a digital token number or transaction account number used in thefunding of the related payment transaction, and additional transactiondata, which may include a transaction amount, transaction time and/ordate, geographic location, consumer data, merchant data, point of saledata, reward data, offer data, loyalty data, product data, issuer data,acquirer data, etc. In some embodiments, each transaction data entry 212may be a transaction message formatted based on one or more standards,such as the ISO 8583 standard. Each transaction message may include aplurality of data elements configured to store the transaction dataincluded therein, including a data element configured to store a primaryaccount number, which may store the digital token number or transactionaccount number used to fund the related payment transaction.

The processing server 102 may include a querying module 214. Thequerying module 214 may be configured to execute queries on databases toidentify information. The querying module 214 may receive one or moredata values or query strings, and may execute a query string basedthereon on an indicated database, such as the token profile database 206and transaction database 210, to identify information stored therein.The querying module 214 may then output the identified information to anappropriate engine or module of the processing server 102 as necessary.The querying module 214 may, for example, execute a query on the tokenprofile database 206 to identify a token profile 208 stored therein thatincludes a computing device identifier corresponding to a deviceidentifier parsed from a data request received by the receiving device202. The querying module 214 may output the identified token profile 208to a data identification module 216.

The data identification module 216 may be configured to analyze data andidentify data based thereon and in data received and retrieved by theother modules and engines of the processing server 102. The dataidentification module 216 may receive an instruction, and, in someinstances, data, may identify data based on the instruction, and mayoutput the identified data. For example, the data identification module216 may receive a token profile 208 identified by the querying module214 (e.g., based on a received data request) with an instruction toidentify related token profiles and transaction data. The dataidentification module 216 may generate a query configured to identifytoken profiles 208 in the token profile database 206 that include thesame transaction account number included in the provided token profile208, which may be passed to the querying module 214 for executionthereby. The related token profiles 208 may be identified and providedto the data identification module 216. The data identification module216 may also be configured to identify transaction data related to theidentified token profiles 208, such as by generating a query configuredto identify transaction data entries 212 in the transaction database 210that include the transaction account number common to the identifiedtoken profiles 208 or that include a digital token number included inone of the identified token profiles 208. The query may be passed to thequerying module 214 for execution thereby in identifying the relatedtransaction data. In some instances, the data identification module 216may generate the query for identification of a limited number oftransaction data entries 212, such as for the most recent transaction orthe most recent transaction for a specific product or at a specificmerchant. In some embodiments, the data identification module 216 mayalso be configured to identify data associated with the attribution ofan advertisement to a transaction. In such embodiments, the dataidentification module 216 may be configured to identify one or moremetrics associated with the attribution of an advertisement to anidentified transaction data entry 212. Such metrics may include, forexample, data regarding the number of exposures to an advertisementbefore purchase, the length of time between first exposure and purchase,the effectiveness of some platforms over others for purchases, etc.

The generation module 218 may be configured to generate data messagesfor transmission by the processing server 102 to other entities, such asto the advertising agency 104. The generation module 218 may receivedata to be included in a data message as input, may generate the datamessage, and may provide the data message as output to another module orengine of the processing server 102 for use thereof. For example, thegeneration module 218 may generate a data message that includescomputing device data included in the identified related token profiles208 and transaction data identified by the data identification module216, which may be passed to the transmitting device 222 for transmissionto the advertising agency 104.

The transmitting device 222 may be configured to transmit data over oneor more networks via one or more network protocols. In some embodiments,the transmitting device 222 may be configured to transmit data over thepayment rails, such as using specially configured infrastructureassociated with payment networks 116 for the transmission of transactionmessages that include sensitive financial data and information, such asidentified payment credentials. In some instances, the transmittingdevice 222 may be configured to transmit data to advertising agencies104, computing devices 106, merchants 114, payment networks 116, andother entities via alternative networks, such as the Internet. In someembodiments, the transmitting device 222 may be comprised of multipledevices, such as different transmitting devices for transmitting dataover different networks, such as a first transmitting device fortransmitting data over the payment rails and a second transmittingdevice for transmitting data over the Internet. The transmitting device222 may electronically transmit data signals that have data superimposedthat may be parsed by a receiving computing device. In some instances,the transmitting device 222 may include one or more modules forsuperimposing, encoding, or otherwise formatting data into data signalssuitable for transmission.

The transmitting device 222 may be configured to electronically transmitdata signals to advertising agencies 104 that are superimposed with datamessages generated by the generation module 218, such as data messagesincluding related computing device data and transaction data. Thetransmitting device 222 may also be configured to electronicallytransmit data signals to the advertising agency 104, payment network116, and other entities that are superimposed with data requests, suchas to request token profile data, computing device data, transactiondata, and other data that may be suitable in performing the functionsdiscussed herein.

In some embodiments, the processing server 102 may also include atransaction processing module 220. The transaction processing module 220may be configured to perform functions related to the processing ofpayment transactions, such as in instances where the processing server102 may be a part of the payment network 116 or other entity involved inthe processing of payment transactions, such as a digitized paymenttoken processing entity. For example, the transaction processing module220 may be configured to remap digital token numbers to transactionaccount numbers (e.g., as identified in corresponding token profiles208), to calculate fraud scores for payment transactions based ontransaction data, identify financial institutions for routing oftransaction messages, etc.

The processing server 102 may also include a memory 224. The memory 224may be configured to store data for use by the processing server 102 inperforming the functions discussed herein. The memory 224 may beconfigured to store data using suitable data formatting methods andschema and may be any suitable type of memory, such as read-only memory,random access memory, etc. The memory 224 may include, for example,encryption keys and algorithms, communication protocols and standards,data formatting standards and protocols, program code for modules andapplication programs of the processing device, and other data that maybe suitable for use by the processing server 102 in the performance ofthe functions disclosed herein as will be apparent to persons havingskill in the relevant art.

Process for Identifying Related Computing Devices and Transaction Data

FIG. 3 illustrates a process for the identification of computing devicesand transaction data related to a provided computing device viadigitized payment tokens and a corresponding transaction account.

In step 302, the advertising agency 104 may distribute an advertisementor other content to a plurality of computing devices 106 using asuitable distribution method, such as by providing the advertisement toone or more content distribution platforms for display to user of thecomputing devices 106, such as in application programs, on web pages,etc. In step 304, the advertising agency 104 may identify a targetcomputing device 106 for which the advertising agency 104 requests dataregarding related computing devices and transaction data. For instance,in one example the advertising agency 104 may identify the targetcomputing device 104 as one where the user interacts with thedistributed advertisement. In another example, the advertising agency104 may identify the target computing device 104 as one where relatedcomputing devices are unknown, such as for enhancement of analytics.

In step 306, the advertising agency 104 may electronically transmit adata signal superimposed with a data request to the processing server102 via the communication network 108 that is superimposed with aspecific computing device identifier that is associated with the targetcomputing device 106 identified by the advertising agency 104 in step304. In step 308, the processing server 102 may register a plurality ofpayment token profiles 208 in the token profile database 206 storedtherein. Each token profile 208 may include data related to a digitizedpayment token including at least a digital token number, an associatedtransaction account number, a computing device identifier, and computingdevice data.

In step 310, the receiving unit 202 of the processing server 102 mayreceive the data signal electronically transmitted by the advertisingagency 104 that includes the data request including the specificcomputing device identifier. The specific computing device identifiermay be parsed from the data request and, in step 312, the queryingmodule 214 of the processing server 102 may execute a query on the tokenprofile database 206 to identify a token profile 208 where the includedcomputing device identifier corresponds to the specific computing deviceidentifier parsed from the data request. The data identification module216 of the processing server 102 may identify the transaction accountnumber included in the identified token profile 208 as the transactionaccount number corresponding to the transaction account associated withthe target computing device 106. In step 314, the data identificationmodule 216 may instruct the querying module 214 to query the tokenprofile database 206 to identify a plurality of related token profiles208 that include the identified transaction account number for theidentification of related computing devices 106.

In step 316, the data identification module 216 of the processing server102 may identify recent payment transactions involving the transactionaccount related to the target computing device 106. The identificationmay involve the providing of a query to the querying module 214 for thequerying of the transaction database 210 to identify transaction dataentries 212 that are related to recent payment transactions (e.g., basedon transaction times and/or dates included therein) that include thetransaction account number associated with the transaction account orthat include a digital token number included in one of the plurality ofrelated token profiles 108 or the identified token profile 108associated with the target computing device 106.

In step 318, the generation module 218 of the processing server 102 maygenerate a data message that includes the identified transaction dataand the computing device data included in the identified related tokenprofiles 208, which may be electronically transmitted to the advertisingagency 104 by the transmitting device 222 of the processing server usingthe communication network 108. In step 320, the advertising agency 104may receive the computing device data and transaction data. In step 322,the advertising agency 104 may identify attributions for purchases madeusing the transaction account based on the distribution ofadvertisements to each of the computing devices based on the computingdevice data. In some instances, the advertising agency 104 may use thecomputing device data and purchase data for identifying patterns andmetrics regarding purchases and platform attribution.

Process for Identifying Computing Devices Related to Transaction Data

FIG. 4 illustrates a process for the identification of related computingdevices that are related to transaction data via digitized paymenttokens and a corresponding transaction account.

In step 402, the advertising agency 104 may distribute an advertisementor other content to a plurality of computing devices 106 using asuitable method. In some instances, the advertising agency 104 may trackwhen the advertisement was sent to which computing device 106 inaddition to known data associated with each computing device 106, suchas for use in determining various statistics and metrics regardingadvertisement distribution and purchase attribution. In step 404, thereceiving device 202 of the processing server 102 may receive atransaction data entry corresponding to a payment transaction processedby the payment network 116. The transaction data entry may include atleast a digital token number or a transaction account number use to fundthe related payment transaction. In some instances, the transaction dataentry may be a transaction message formatted based on one or morestandards, such as the ISO 8583 standard, which may include a dataelement configured to store a primary account number, which may storethe digital token number or transaction account number.

In step 406, the data identification module 216 of the processing server102 may identify a token profile 208 involved in the payment transactionrelated to the received transaction data entry. The data identificationmodule 216 may generate a query for execution by the querying module 214of the processing server 102 to query the token profile database 206 toidentify a specific token profile 208 that includes the digital tokennumber included in the received transaction data entry. The transactionaccount number included therein may be identified as related to thetransaction account involved in the payment transaction. In embodimentswhere the transaction data entry may include the transaction accountnumber, step 406 may be an optional step.

In step 408, the data identification module 216 may identify a pluralityof computing devices 106 related to the computing device 106corresponding to the identified specific token profile 208. Theidentification of the plurality of computing devices 106 may includegenerating a query to be executed by the querying module 214 on thetoken profile database 206 to identify a plurality of related tokenprofiles 208 where the included transaction account number correspondsto the transaction account number included in the specific token profile208 and/or the received transaction data. The computing device dataincluded in each of the plurality of related token profiles 208 may thenbe identified as computing device data related to the computing devices106 related to the transaction account used to fund the paymenttransaction. In step 410, the data identification module 216 mayidentify an advertising agency 104 associated with the transactionaccount, one of the plurality of computing devices 106, and/or thepayment transaction. Identification of the advertising agency 104 mayinclude identifying data associated therewith included in the identifiedtoken profiles 208 or stored in the memory 224 that includes acorresponding between the advertising agency 104 and the transactiondata entry. For example, the payment transaction may involve thepurchase of a product (e.g., indicated in product data included therein)for which the advertising agency 104 is associated (e.g., as stored inthe memory 224 based on data provided by the advertising agency 104).

In step 412, the generation module 218 of the processing server 102 maygenerate a data message that includes the computing device dataassociated with each of the plurality of computing devices 106, as wellas the transaction data included in the received transaction data entry.The transmitting device 222 of the processing server 102 mayelectronically transmit the generated data message to the advertisingagency 104 via superimposition on a data signal electronicallytransmitted to the advertising agency 104 using the communicationnetwork 108. In step 414, the advertising agency 104 may receive thedata signal and parse the signal to obtain the data message and dataincluded therein, and, in step 416, may identify attributions for thepurchase based on the computing device data and data related to thedistribution of advertisements thereto.

First Exemplary Method for Identifying a Plurality of Related ComputingDevices Related to a Transaction Account

FIG. 5 illustrates a method 500 for the identification of a plurality ofcomputing devices related to a transaction account via digitized paymenttokens that is associated with a computing device identified in areceived data request.

In step 502, a plurality of token profiles (e.g., token profiles 208)may be stored in a token profile database (e.g., the token profiledatabase 206) of a processing server (e.g., the processing server 102),wherein each token profile includes a structured data set related to apayment token including at least a digital token number, an associatedtransaction account number, a computing device identifier, and computingdevice data. In step 504, a plurality of transaction data entries (e.g.,transaction data entries 212) may be stored in a transaction database(e.g., the transaction database 210) of a processing server, whereineach transaction data entry includes a structured data set related to anelectronic transaction including at least a specific digital tokennumber or specific transaction account number used in funding therelated electronic transaction and transaction data.

In step 506, a data signal superimposed with a related device requestmay be received by a receiving device (e.g., the receiving device 202)of the processing server that is electronically transmitted from a thirdparty entity (e.g., the advertising agency 104), wherein the relateddevice request includes at least a specific computing device identifier.In step 508, a query may be executed by a querying module (e.g., thequerying module 214) of the processing server on the token profiledatabase to identify a specific token profile where the includedcomputing device identifier corresponds to the specific computing deviceidentifier. In step 510, a query may be executed by the querying moduleof the processing server on the token profile database to identify aplurality of related token profiles where the included associatedtransaction account number corresponds to the associated transactionaccount number included in the identified specific token profile.

In step 512, a query may be executed by the querying module of theprocessing server on the transaction database to identify a specifictransaction data entry where the included specific digital token numberor specific transaction account number corresponds to a digital tokennumber or associated transaction account number included in at least oneof the identified plurality of related token profiles or the identifiedspecific token profile. In step 514, a data signal may be electronicallytransmitted to the third party entity by a transmitting device (e.g.,the transmitting device 222) of the processing server that issuperimposed with at least the transaction data included in theidentified specific transaction data entry and at least one of: thecomputing device identifier and computing device data included in eachof the identified plurality of related token profiles.

In one embodiment, each transaction data entry may be a transactionmessage formatted based on one or more standards, and the specificdigital token number or specific transaction account number included ineach transaction data entry is stored in a data element included in therespective transaction message configured to store a primary accountnumber. In a further embodiment, the one or more standards may includethe ISO 8583 standard. In some embodiments, the computing device datamay include at least one of: make, manufacturer, model, form factor,architecture, type, and geographic location.

Second Exemplary Method for Identifying a Plurality of Related ComputingDevices Related to a Transaction Account

FIG. 6 illustrates a method 600 for the identification of a plurality ofcomputing devices related to a transaction account used in a paymenttransaction related to received transaction data via digitized paymenttokens.

In step 602, a plurality of token profiles (e.g., token profiles 208)may be stored in a token profile database (e.g., the token profiledatabase 206) of a processing server (e.g., the processing server 102),wherein each token profile includes a structured data set related to apayment token including at least a digital token number, an associatedtransaction account number, a computing device identifier, and computingdevice data. In step 604, a transaction data entry related to anelectronic transaction may be received by a receiving device (e.g., thereceiving device 202) of the processing server, wherein the transactiondata entry includes at least transaction data and one of: a specifictransaction account number or a specific digital token number associatedwith a specific transaction account number.

In step 606, a query may be executed by a querying module (e.g., thequerying module 214) of the processing server on the token profiledatabase to identify a plurality of related token profiles where theincluded associated transaction account number corresponds to thespecific transaction account number. In step 608, a data identificationmodule (e.g., the data identification module 216) of the processingserver may identify a third party entity (e.g., the advertising agency104) associated with at least one token profile included in theidentified plurality of related token profiles. In step 610, a datasignal may be electronically transmitted by a transmitting device (e.g.,the transmitting device 222) of the processing server to the identifiedthird party entity, where the data signal is superimposed with at leastthe transaction data included in the transaction data entry and at leastone of: the computing device identifier and computing device dataincluded in each of the identified plurality of related token profiles.

In one embodiment, each transaction data entry may be a transactionmessage formatted based on one or more standards, and the specificdigital token number or specific transaction account number included ineach transaction data entry is stored in a data element included in therespective transaction message configured to store a primary accountnumber. In a further embodiment, the one or more standards may includethe ISO 8583 standard. In some embodiments, the computing device datamay include at least one of: make, manufacturer, model, form factor,architecture, type, and geographic location.

In one embodiment, the method 600 may also include executing, by thequerying module of the processing server, a query on the token profiledatabase to identify a specific token profile where the included digitaltoken number corresponds to the specific digital token number includedin the received transaction data entry if the received transaction dataentry includes a specific digital token number, wherein the associatedspecific transaction account number corresponds to the associatedtransaction account number included in the identified specific tokenprofile. In some embodiments, the at least one token profile associatedwith the third party entity may be included in the identified pluralityof related token profiles includes communication data associated withthe third party entity, and identifying the third party entity mayinclude executing, by the querying module of the processing server, aquery on the identified plurality of related token profiles to identifythe at least one token profile including communication data associatedwith the third party entity.

Payment Transaction Processing System and Process

FIG. 7 illustrates a transaction processing system and a process 700 forthe processing of payment transactions in the system. The process 700and steps included therein may be performed by one or more components ofthe system 100 discussed above, such as the processing server 102,computing devices 106, merchant 114, payment network 116, etc. Theprocessing of payment transactions using the system and process 700illustrated in FIG. 7 and discussed below may utilize the payment rails,which may be comprised of the computing devices and infrastructureutilized to perform the steps of the process 700 as specially configuredand programmed by the entities discussed below, including thetransaction processing server 712, which may be associated with one ormore payment networks configured to processing payment transactions. Itwill be apparent to persons having skill in the relevant art that theprocess 700 may be incorporated into the processes illustrated in FIGS.3-6, discussed above, with respect to the step or steps involved in theprocessing of a payment transaction. In addition, the entities discussedherein for performing the process 700 may include one or more computingdevices or systems configured to perform the functions discussed below.For instance, the merchant 706 may be comprised of one or more point ofsale devices, a local communication network, a computing server, andother devices configured to perform the functions discussed below.

In step 720, an issuing financial institution 702 may issue a paymentcard or other suitable payment instrument to a consumer 704. The issuingfinancial institution may be a financial institution, such as a bank, orother suitable type of entity that administers and manages paymentaccounts and/or payment instruments for use with payment accounts thatcan be used to fund payment transactions. The consumer 704 may have atransaction account with the issuing financial institution 702 for whichthe issued payment card is associated, such that, when used in a paymenttransaction, the payment transaction is funded by the associatedtransaction account. In some embodiments, the payment card may be issuedto the consumer 704 physically. In other embodiments, the payment cardmay be a virtual payment card or otherwise provisioned to the consumer704 in an electronic format.

In step 722, the consumer 704 may present the issued payment card to amerchant 706 for use in funding a payment transaction. The merchant 706may be a business, another consumer, or any entity that may engage in apayment transaction with the consumer 704. The payment card may bepresented by the consumer 704 via providing the physical card to themerchant 706, electronically transmitting (e.g., via near fieldcommunication, wireless transmission, or other suitable electronictransmission type and protocol) payment details for the payment card, orinitiating transmission of payment details to the merchant 706 via athird party. The merchant 706 may receive the payment details (e.g., viathe electronic transmission, via reading them from a physical paymentcard, etc.), which may include at least a transaction account numberassociated with the payment card and/or associated transaction account.In some instances, the payment details may include one or moreapplication cryptograms, which may be used in the processing of thepayment transaction.

In step 724, the merchant 706 may enter transaction details into a pointof sale computing system. The transaction details may include thepayment details provided by the consumer 704 associated with the paymentcard and additional details associated with the transaction, such as atransaction amount, time and/or date, product data, offer data, loyaltydata, reward data, merchant data, consumer data, point of sale data,etc. Transaction details may be entered into the point of sale system ofthe merchant 706 via one or more input devices, such as an optical barcode scanner configured to scan product bar codes, a keyboard configuredto receive product codes input by a user, etc. The merchant point ofsale system may be a specifically configured computing device and/orspecial purpose computing device intended for the purpose of processingelectronic financial transactions and communicating with a paymentnetwork (e.g., via the payment rails). The merchant point of sale systemmay be an electronic device upon which a point of sale systemapplication is run, wherein the application causes the electronic deviceto receive and communicated electronic financial transaction informationto a payment network. In some embodiments, the merchant 706 may be anonline retailer in an e-commerce transaction. In such embodiments, thetransaction details may be entered in a shopping cart or otherrepository for storing transaction data in an electronic transaction aswill be apparent to persons having skill in the relevant art.

In step 726, the merchant 706 may electronically transmit a data signalsuperimposed with transaction data to a gateway processor 708. Thegateway processor 708 may be an entity configured to receive transactiondetails from a merchant 706 for formatting and transmission to anacquiring financial institution 710. In some instances, a gatewayprocessor 708 may be associated with a plurality of merchants 706 and aplurality of acquiring financial institutions 710. In such instances,the gateway processor 708 may receive transaction details for aplurality of different transactions involving various merchants, whichmay be forwarded on to appropriate acquiring financial institutions 710.By having relationships with multiple acquiring financial institutions710 and having the requisite infrastructure to communicate withfinancial institutions using the payment rails, such as usingapplication programming interfaces associated with the gateway processor708 or financial institutions used for the submission, receipt, andretrieval of data, a gateway processor 708 may act as an intermediaryfor a merchant 706 to be able to conduct payment transactions via asingle communication channel and format with the gateway processor 708,without having to maintain relationships with multiple acquiringfinancial institutions 710 and payment processors and the hardwareassociated thereto. Acquiring financial institutions 710 may befinancial institutions, such as banks, or other entities thatadministers and manages payment accounts and/or payment instruments foruse with payment accounts. In some instances, acquiring financialinstitutions 710 may manage transaction accounts for merchants 706. Insome cases, a single financial institution may operate as both anissuing financial institution 702 and an acquiring financial institution710.

The data signal transmitted from the merchant 706 to the gatewayprocessor 708 may be superimposed with the transaction details for thepayment transaction, which may be formatted based on one or morestandards. In some embodiments, the standards may be set forth by thegateway processor 708, which may use a unique, proprietary format forthe transmission of transaction data to/from the gateway processor 708.In other embodiments, a public standard may be used, such as theInternational Organization for Standardization's ISO 8783 standard. Thestandard may indicate the types of data that may be included, theformatting of the data, how the data is to be stored and transmitted,and other criteria for the transmission of the transaction data to thegateway processor 708.

In step 728, the gateway processor 708 may parse the transaction datasignal to obtain the transaction data superimposed thereon and mayformat the transaction data as necessary. The formatting of thetransaction data may be performed by the gateway processor 708 based onthe proprietary standards of the gateway processor 708 or an acquiringfinancial institution 710 associated with the payment transaction. Theproprietary standards may specify the type of data included in thetransaction data and the format for storage and transmission of thedata. The acquiring financial institution 710 may be identified by thegateway processor 708 using the transaction data, such as by parsing thetransaction data (e.g., deconstructing into data elements) to obtain anaccount identifier included therein associated with the acquiringfinancial institution 710. In some instances, the gateway processor 708may then format the transaction data based on the identified acquiringfinancial institution 710, such as to comply with standards offormatting specified by the acquiring financial institution 710.

In some embodiments, the identified acquiring financial institution 710may be associated with the merchant 706 involved in the paymenttransaction, and, in some cases, may manage a transaction accountassociated with the merchant 706.

In step 730, the gateway processor 708 may electronically transmit adata signal superimposed with the formatted transaction data to theidentified acquiring financial institution 710. The acquiring financialinstitution 710 may receive the data signal and parse the signal toobtain the formatted transaction data superimposed thereon. In step 732,the acquiring financial institution may generate an authorizationrequest for the payment transaction based on the formatted transactiondata. The authorization request may be a specially formatted transactionmessage that is formatted pursuant to one or more standards, such as theISO 8783 standard and standards set forth by a payment processor used toprocess the payment transaction, such as a payment network. Theauthorization request may be a transaction message that includes amessage type indicator indicative of an authorization request, which mayindicate that the merchant 706 involved in the payment transaction isrequesting payment or a promise of payment from the issuing financialinstitution 702 for the transaction. The authorization request mayinclude a plurality of data elements, each data element being configuredto store data as set forth in the associated standards, such as forstoring an account number, application cryptogram, transaction amount,issuing financial institution 702 information, etc.

In step 734, the acquiring financial institution 710 may electronicallytransmit the authorization request to a transaction processing server712 for processing. The transaction processing server 712 may becomprised of one or more computing devices as part of a payment networkconfigured to process payment transactions. In some embodiments, theauthorization request may be transmitted by a transaction processor atthe acquiring financial institution 710 or other entity associated withthe acquiring financial institution. The transaction processor may beone or more computing devices that include a plurality of communicationchannels for communication with the transaction processing server 712for the transmission of transaction messages and other data to and fromthe transaction processing server 712. In some embodiments, the paymentnetwork associated with the transaction processing server 712 may own oroperate each transaction processor such that the payment network maymaintain control over the communication of transaction messages to andfrom the transaction processing server 712 for network and informationalsecurity.

In step 736, the transaction processing server 712 may performvalue-added services for the payment transaction. Value-added servicesmay be services specified by the issuing financial institution 702 thatmay provide additional value to the issuing financial institution 702 orthe consumer 704 in the processing of payment transactions. Value-addedservices may include, for example, fraud scoring, transaction or accountcontrols, account number mapping, offer redemption, loyalty processing,etc. For instance, when the transaction processing server 712 receivesthe transaction, a fraud score for the transaction may be calculatedbased on the data included therein and one or more fraud scoringalgorithms and/or engines. In some instances, the transaction processingserver 712 may first identify the issuing financial institution 702associated with the transaction, and then identify any servicesindicated by the issuing financial institution 702 to be performed. Theissuing financial institution 702 may be identified, for example, bydata included in a specific data element included in the authorizationrequest, such as an issuer identification number. In another example,the issuing financial institution 702 may be identified by the primaryaccount number stored in the authorization request, such as by using aportion of the primary account number (e.g., a bank identificationnumber) for identification.

In step 738, the transaction processing server 712 may electronicallytransmit the authorization request to the issuing financial institution702. In some instances, the authorization request may be modified, oradditional data included in or transmitted accompanying theauthorization request as a result of the performance of value-addedservices by the transaction processing server 712. In some embodiments,the authorization request may be transmitted to a transaction processor(e.g., owned or operated by the transaction processing server 712)situated at the issuing financial institution 702 or an entityassociated thereof, which may forward the authorization request to theissuing financial institution 702.

In step 740, the issuing financial institution 702 may authorize thetransaction account for payment of the payment transaction. Theauthorization may be based on an available credit amount for thetransaction account and the transaction amount for the paymenttransaction, fraud scores provided by the transaction processing server712, and other considerations that will be apparent to persons havingskill in the relevant art. The issuing financial institution 702 maymodify the authorization request to include a response code indicatingapproval (e.g., or denial if the transaction is to be denied) of thepayment transaction. The issuing financial institution 702 may alsomodify a message type indicator for the transaction message to indicatethat the transaction message is changed to be an authorization response.In step 742, the issuing financial institution 702 may transmit (e.g.,via a transaction processor) the authorization response to thetransaction processing server 712.

In step 744, the transaction processing server 712 may forward theauthorization response to the acquiring financial institution 710 (e.g.,via a transaction processor). In step 746, the acquiring financialinstitution may generate a response message indicating approval ordenial of the payment transaction as indicated in the response code ofthe authorization response, and may transmit the response message to thegateway processor 708 using the standards and protocols set forth by thegateway processor 708. In step 748, the gateway processor 708 mayforward the response message to the merchant 706 using the appropriatestandards and protocols. In step 770, the merchant 706 may then providethe products purchased by the consumer 704 as part of the paymenttransaction to the consumer 704.

In some embodiments, once the process 700 has completed, payment fromthe issuing financial institution 702 to the acquiring financialinstitution 710 may be performed. In some instances, the payment may bemade immediately or within one business day. In other instances, thepayment may be made after a period of time, and in response to thesubmission of a clearing request from the acquiring financialinstitution 710 to the issuing financial institution 702 via thetransaction processing server 702. In such instances, clearing requestsfor multiple payment transactions may be aggregated into a singleclearing request, which may be used by the transaction processing server712 to identify overall payments to be made by whom and to whom forsettlement of payment transactions.

In some instances, the system may also be configured to perform theprocessing of payment transactions in instances where communicationpaths may be unavailable. For example, if the issuing financialinstitution is unavailable to perform authorization of the transactionaccount (e.g., in step 740), the transaction processing server 712 maybe configured to perform authorization of transactions on behalf of theissuing financial institution 702. Such actions may be referred to as“stand-in processing,” where the transaction processing server “standsin” as the issuing financial institution 702. In such instances, thetransaction processing server 712 may utilize rules set forth by theissuing financial institution 702 to determine approval or denial of thepayment transaction, and may modify the transaction message accordinglyprior to forwarding to the acquiring financial institution 710 in step744. The transaction processing server 712 may retain data associatedwith transactions for which the transaction processing server 712 standsin, and may transmit the retained data to the issuing financialinstitution 702 once communication is reestablished. The issuingfinancial institution 702 may then process transaction accountsaccordingly to accommodate for the time of lost communication.

In another example, if the transaction processing server 712 isunavailable for submission of the authorization request by the acquiringfinancial institution 710, then the transaction processor at theacquiring financial institution 710 may be configured to perform theprocessing of the transaction processing server 712 and the issuingfinancial institution 702. The transaction processor may include rulesand data suitable for use in making a determination of approval ordenial of the payment transaction based on the data included therein.For instance, the issuing financial institution 702 and/or transactionprocessing server 712 may set limits on transaction type, transactionamount, etc. that may be stored in the transaction processor and used todetermine approval or denial of a payment transaction based thereon. Insuch instances, the acquiring financial institution 710 may receive anauthorization response for the payment transaction even if thetransaction processing server 712 is unavailable, ensuring thattransactions are processed and no downtime is experienced even ininstances where communication is unavailable. In such cases, thetransaction processor may store transaction details for the paymenttransactions, which may be transmitted to the transaction processingserver 712 (e.g., and from there to the associated issuing financialinstitutions 702) once communication is reestablished.

In some embodiments, transaction processors may be configured to includea plurality of different communication channels, which may utilizemultiple communication cards and/or devices, to communicate with thetransaction processing server 712 for the sending and receiving oftransaction messages. For example, a transaction processor may becomprised of multiple computing devices, each having multiplecommunication ports that are connected to the transaction processingserver 712. In such embodiments, the transaction processor may cyclethrough the communication channels when transmitting transactionmessages to the transaction processing server 712, to alleviate networkcongestion and ensure faster, smoother communications. Furthermore, ininstances where a communication channel may be interrupted or otherwiseunavailable, alternative communication channels may thereby beavailable, to further increase the uptime of the network.

In some embodiments, transaction processors may be configured tocommunicate directly with other transaction processors. For example, atransaction processor at an acquiring financial institution 710 mayidentify that an authorization request involves an issuing financialinstitution 702 (e.g., via the bank identification number included inthe transaction message) for which no value-added services are required.The transaction processor at the acquiring financial institution 710 maythen transmit the authorization request directly to the transactionprocessor at the issuing financial institution 702 (e.g., without theauthorization request passing through the transaction processing server712), where the issuing financial institution 702 may process thetransaction accordingly.

The methods discussed above for the processing of payment transactionsthat utilize multiple methods of communication using multiplecommunication channels, and includes fail safes to provide for theprocessing of payment transactions at multiple points in the process andat multiple locations in the system, as well as redundancies to ensurethat communications arrive at their destination successfully even ininstances of interruptions, may provide for a robust system that ensuresthat payment transactions are always processed successfully with minimalerror and interruption. This advanced network and its infrastructure andtopology may be commonly referred to as “payment rails,” wheretransaction data may be submitted to the payment rails from merchants atmillions of different points of sale, to be routed through theinfrastructure to the appropriate transaction processing servers 712 forprocessing. The payment rails may be such that a general purposecomputing device may be unable to properly format or submitcommunications to the rails, without specialized programming and/orconfiguration. Through the specialized purposing of a computing device,the computing device may be configured to submit transaction data to theappropriate entity (e.g., a gateway processor 708, acquiring financialinstitution 710, etc.) for processing using this advanced network, andto quickly and efficiently receive a response regarding the ability fora consumer 704 to fund the payment transaction.

Computer System Architecture

FIG. 8 illustrates a computer system 800 in which embodiments of thepresent disclosure, or portions thereof, may be implemented ascomputer-readable code. For example, the processing server 102 of FIG. 1may be implemented in the computer system 800 using hardware, software,firmware, non-transitory computer readable media having instructionsstored thereon, or a combination thereof and may be implemented in oneor more computer systems or other processing systems. Hardware,software, or any combination thereof may embody modules and componentsused to implement the methods of FIGS. 3-7.

If programmable logic is used, such logic may execute on a commerciallyavailable processing platform or a special purpose device. A personhaving ordinary skill in the art may appreciate that embodiments of thedisclosed subject matter can be practiced with various computer systemconfigurations, including multi-core multiprocessor systems,minicomputers, mainframe computers, computers linked or clustered withdistributed functions, as well as pervasive or miniature computers thatmay be embedded into virtually any device. For instance, at least oneprocessor device and a memory may be used to implement the abovedescribed embodiments.

A processor unit or device as discussed herein may be a singleprocessor, a plurality of processors, or combinations thereof. Processordevices may have one or more processor “cores.” The terms “computerprogram medium,” “non-transitory computer readable medium,” and“computer usable medium” as discussed herein are used to generally referto tangible media such as a removable storage unit 818, a removablestorage unit 822, and a hard disk installed in hard disk drive 812.

Various embodiments of the present disclosure are described in terms ofthis example computer system 800. After reading this description, itwill become apparent to a person skilled in the relevant art how toimplement the present disclosure using other computer systems and/orcomputer architectures. Although operations may be described as asequential process, some of the operations may in fact be performed inparallel, concurrently, and/or in a distributed environment, and withprogram code stored locally or remotely for access by single ormulti-processor machines. In addition, in some embodiments the order ofoperations may be rearranged without departing from the spirit of thedisclosed subject matter.

Processor device 804 may be a special purpose or a general purposeprocessor device specifically configured to perform the functionsdiscussed herein. The processor device 804 may be connected to acommunications infrastructure 806, such as a bus, message queue,network, multi-core message-passing scheme, etc. The network may be anynetwork suitable for performing the functions as disclosed herein andmay include a local area network (LAN), a wide area network (WAN), awireless network (e.g., WiFi), a mobile communication network, asatellite network, the Internet, fiber optic, coaxial cable, infrared,radio frequency (RF), or any combination thereof. Other suitable networktypes and configurations will be apparent to persons having skill in therelevant art. The computer system 800 may also include a main memory 808(e.g., random access memory, read-only memory, etc.), and may alsoinclude a secondary memory 810. The secondary memory 810 may include thehard disk drive 812 and a removable storage drive 814, such as a floppydisk drive, a magnetic tape drive, an optical disk drive, a flashmemory, etc.

The removable storage drive 814 may read from and/or write to theremovable storage unit 818 in a well-known manner. The removable storageunit 818 may include a removable storage media that may be read by andwritten to by the removable storage drive 814. For example, if theremovable storage drive 814 is a floppy disk drive or universal serialbus port, the removable storage unit 818 may be a floppy disk orportable flash drive, respectively. In one embodiment, the removablestorage unit 818 may be non-transitory computer readable recordingmedia.

In some embodiments, the secondary memory 810 may include alternativemeans for allowing computer programs or other instructions to be loadedinto the computer system 800, for example, the removable storage unit822 and an interface 820. Examples of such means may include a programcartridge and cartridge interface (e.g., as found in video gamesystems), a removable memory chip (e.g., EEPROM, PROM, etc.) andassociated socket, and other removable storage units 822 and interfaces820 as will be apparent to persons having skill in the relevant art.

Data stored in the computer system 800 (e.g., in the main memory 808and/or the secondary memory 810) may be stored on any type of suitablecomputer readable media, such as optical storage (e.g., a compact disc,digital versatile disc, Blu-ray disc, etc.) or magnetic tape storage(e.g., a hard disk drive). The data may be configured in any type ofsuitable database configuration, such as a relational database, astructured query language (SQL) database, a distributed database, anobject database, etc. Suitable configurations and storage types will beapparent to persons having skill in the relevant art.

The computer system 800 may also include a communications interface 824.The communications interface 824 may be configured to allow software anddata to be transferred between the computer system 800 and externaldevices. Exemplary communications interfaces 824 may include a modem, anetwork interface (e.g., an Ethernet card), a communications port, aPCMCIA slot and card, etc. Software and data transferred via thecommunications interface 824 may be in the form of signals, which may beelectronic, electromagnetic, optical, or other signals as will beapparent to persons having skill in the relevant art. The signals maytravel via a communications path 826, which may be configured to carrythe signals and may be implemented using wire, cable, fiber optics, aphone line, a cellular phone link, a radio frequency link, etc.

The computer system 800 may further include a display interface 802. Thedisplay interface 802 may be configured to allow data to be transferredbetween the computer system 800 and external display 830. Exemplarydisplay interfaces 802 may include high-definition multimedia interface(HDMI), digital visual interface (DVI), video graphics array (VGA), etc.The display 830 may be any suitable type of display for displaying datatransmitted via the display interface 802 of the computer system 800,including a cathode ray tube (CRT) display, liquid crystal display(LCD), light-emitting diode (LED) display, capacitive touch display,thin-film transistor (TFT) display, etc.

Computer program medium and computer usable medium may refer tomemories, such as the main memory 808 and secondary memory 810, whichmay be memory semiconductors (e.g., DRAMs, etc.). These computer programproducts may be means for providing software to the computer system 800.Computer programs (e.g., computer control logic) may be stored in themain memory 808 and/or the secondary memory 810. Computer programs mayalso be received via the communications interface 824. Such computerprograms, when executed, may enable computer system 800 to implement thepresent methods as discussed herein. In particular, the computerprograms, when executed, may enable processor device 804 to implementthe methods illustrated by FIGS. 3-7, as discussed herein. Accordingly,such computer programs may represent controllers of the computer system800. Where the present disclosure is implemented using software, thesoftware may be stored in a computer program product and loaded into thecomputer system 800 using the removable storage drive 814, interface820, and hard disk drive 812, or communications interface 824.

The processor device 804 may comprise one or more modules or enginesconfigured to perform the functions of the computer system 800. Each ofthe modules or engines may be implemented using hardware and, in someinstances, may also utilize software, such as corresponding to programcode and/or programs stored in the main memory 808 or secondary memory810. In such instances, program code may be compiled by the processordevice 804 (e.g., by a compiling module or engine) prior to execution bythe hardware of the computer system 800. For example, the program codemay be source code written in a programming language that is translatedinto a lower level language, such as assembly language or machine code,for execution by the processor device 804 and/or any additional hardwarecomponents of the computer system 800. The process of compiling mayinclude the use of lexical analysis, preprocessing, parsing, semanticanalysis, syntax-directed translation, code generation, codeoptimization, and any other techniques that may be suitable fortranslation of program code into a lower level language suitable forcontrolling the computer system 800 to perform the functions disclosedherein. It will be apparent to persons having skill in the relevant artthat such processes result in the computer system 800 being a speciallyconfigured computer system 800 uniquely programmed to perform thefunctions discussed above.

Techniques consistent with the present disclosure provide, among otherfeatures, systems and methods for identifying a plurality of relatedcomputing devices related to a transaction account. While variousexemplary embodiments of the disclosed system and method have beendescribed above it should be understood that they have been presentedfor purposes of example only, not limitations. It is not exhaustive anddoes not limit the disclosure to the precise form disclosed.Modifications and variations are possible in light of the aboveteachings or may be acquired from practicing of the disclosure, withoutdeparting from the breadth or scope.

What is claimed is:
 1. A method for identifying a plurality of relatedcomputing devices related to a transaction account, comprising: storing,in a token profile database of a processing server, a plurality of tokenprofiles, wherein each token profile includes a structured data setrelated to a payment token including at least a digital token number, anassociated transaction account number, a computing device identifier,and computing device data, and where the associated transaction accountnumber is tied to a single transaction account; storing, in atransaction database of the processing server, a plurality oftransaction data entries, wherein each transaction data entry includes astructured data set related to an electronic transaction including atleast a specific digital token number or specific transaction accountnumber used in funding the related electronic transaction andtransaction data; receiving, by a receiving device of the processingserver, a data signal superimposed with a related device requestelectronically transmitted from a third party entity, wherein therelated device request includes at least a specific computing deviceidentifier; executing, by a querying module of the processing server, aquery on the token profile database to identify a specific token profilewhere the included computing device identifier corresponds to thespecific computing device identifier; executing, by the querying moduleof the processing server, a query on the token profile database toidentify a plurality of related token profiles where the includedassociated transaction account number corresponds to the associatedtransaction account number included in the identified specific tokenprofile and where the computing device identifier included in each ofthe plurality of related token profiles is unique across the pluralityof related token profiles and the specific token profile; executing, bythe querying module of the processing server, a query on the transactiondatabase to identify a specific transaction data entry where theincluded specific digital token number or specific transaction accountnumber corresponds to a digital token number or associated transactionaccount number included in at least one of the identified plurality ofrelated token profiles or the identified specific token profile; andelectronically transmitting, by a transmitting device of the processingserver, a data signal to the third party entity superimposed with atleast the transaction data included in the identified specifictransaction data entry and at least one of: the computing deviceidentifier and computing device data included in each of the identifiedplurality of related token profiles.
 2. The method of claim 1, whereineach transaction data entry is a transaction message formatted based onone or more standards, and the specific digital token number or specifictransaction account number included in each transaction data entry isstored in a data element included in the respective transaction messageconfigured to store a primary account number.
 3. The method of claim 2,wherein the one or more standards includes the ISO 8583 standard.
 4. Themethod of claim 1, wherein the computing device data includes at leastone of: make, manufacturer, model, form factor, architecture, type, andgeographic location.
 5. A method for identifying a plurality of relatedcomputing devices related to a transaction account, comprising: storing,in a token profile database of a processing server, a plurality of tokenprofiles, wherein each token profile includes a structured data setrelated to a payment token including at least a digital token number, anassociated transaction account number, a computing device identifier,and computing device data, and where the associated transaction accountnumber is tied to a single transaction account; receiving, by areceiving device of the processing server, a transaction data entryrelated to an electronic transaction, wherein the transaction data entryincludes at least transaction data and one of: a specific transactionaccount number or a specific digital token number associated with aspecific transaction account number; executing, by a querying module ofthe processing server, a query on the token profile database to identifya plurality of related token profiles where the included associatedtransaction account number corresponds to the specific transactionaccount number and where the computing device identifier included ineach of the plurality of related token profiles is unique across theplurality of related token profiles; identifying, by a dataidentification module of the processing server, a third party entityassociated with at least one token profile included in the identifiedplurality of related token profiles; and electronically transmitting, bya transmitting device of the processing server, a data signal to theidentified third party entity superimposed with at least the transactiondata included in the transaction data entry and at least one of: thecomputing device identifier and computing device data included in eachof the identified plurality of related token profiles.
 6. The method ofclaim 5, wherein the transaction data entry is a transaction messageformatted based on one or more standards, and the specific digital tokennumber or specific transaction account number included in thetransaction data entry is stored in a data element included in thetransaction message configured to store a primary account number.
 7. Themethod of claim 1, wherein the one or more standards includes the ISO8583 standard.
 8. The method of claim 5, further comprising: executing,by the querying module of the processing server, a query on the tokenprofile database to identify a specific token profile where the includeddigital token number corresponds to the specific digital token numberincluded in the received transaction data entry if the receivedtransaction data entry includes a specific digital token number, whereinthe associated specific transaction account number corresponds to theassociated transaction account number included in the identifiedspecific token profile.
 9. The method of claim 5, wherein the at leastone token profile associated with the third party entity included in theidentified plurality of related token profiles includes communicationdata associated with the third party entity, and identifying the thirdparty entity includes executing, by the querying module of theprocessing server, a query on the identified plurality of related tokenprofiles to identify the at least one token profile includingcommunication data associated with the third party entity.
 10. Themethod of claim 5, wherein the computing device data includes at leastone of: make, manufacturer, model, form factor, architecture, type, andgeographic location.
 11. A system for identifying a plurality of relatedcomputing devices related to a transaction account, comprising: a tokenprofile database of a processing server configured to store a pluralityof token profiles, wherein each token profile includes a structured dataset related to a payment token including at least a digital tokennumber, an associated transaction account number, a computing deviceidentifier, and computing device data, and where the associatedtransaction account number is tied to a single transaction account; atransaction database of the processing server configured to store aplurality of transaction data entries, wherein each transaction dataentry includes a structured data set related to an electronictransaction including at least a specific digital token number orspecific transaction account number used in funding the relatedelectronic transaction and transaction data; a receiving device of theprocessing server configured to receive a data signal superimposed witha related device request electronically transmitted from a third partyentity, wherein the related device request includes at least a specificcomputing device identifier; a querying module of the processing serverconfigured to execute a query on the token profile database to identifya specific token profile where the included computing device identifiercorresponds to the specific device identifier, a query on the tokenprofile database to identify a plurality of related token profiles wherethe included associated transaction account number corresponds to theassociated transaction account number included in the identifiedspecific token profile and where the computing device identifierincluded in each of the plurality of related token profiles is uniqueacross the plurality of related token profiles and the specific tokenprofile, and a query on the transaction database to identify a specifictransaction data entry where the included specific digital token numberor specific transaction account number corresponds to a digital tokennumber or associated transaction account number included in at least oneof the identified plurality of related token profiles or the identifiedspecific token profile; and a transmitting device of the processingserver configured to electronically transmit a data signal to the thirdparty entity superimposed with at least the transaction data included inthe identified specific transaction data entry and at least one of: thecomputing device identifier and computing device data included in eachof the identified plurality of related token profiles.
 12. The system ofclaim 11, wherein each transaction data entry is a transaction messageformatted based on one or more standards, and the specific digital tokennumber or specific transaction account number included in eachtransaction data entry is stored in a data element included in therespective transaction message configured to store a primary accountnumber.
 13. The system of claim 12, wherein the one or more standardsincludes the ISO 8583 standard.
 14. The system of claim 11, wherein thecomputing device data includes at least one of: make, manufacturer,model, form factor, architecture, type, and geographic location.
 15. Asystem for identifying a plurality of related computing devices relatedto a transaction account, comprising: A token profile database of aprocessing server configured to store a plurality of token profiles,wherein each token profile includes a structured data set related to apayment token including at least a digital token number, an associatedtransaction account number, a computing device identifier, and computingdevice data, and where the associated transaction account number is tiedto a single transaction account; a receiving device of the processingserver configured to receive a transaction data entry related to anelectronic transaction, wherein the transaction data entry includes atleast transaction data and one of: a specific transaction account numberor a specific digital token number associated with a specifictransaction account number; a querying module of the processing serverconfigured to execute a query on the token profile database to identifya plurality of related token profiles where the included associatedtransaction account number corresponds to the specific transactionaccount number and where the computing device identifier included ineach of the plurality of related token profiles is unique across theplurality of related token profiles; a data identification module of theprocessing server configured to identify a third party entity associatedwith at least one token profile included in the identified plurality ofrelated token profiles; and a transmitting device of the processingserver configured to electronically transmit a data signal to theidentified third party entity superimposed with at least the transactiondata included in the transaction data entry and at least one of: thecomputing device identifier and computing device data included in eachof the identified plurality of related token profiles.
 16. The system ofclaim 15, wherein the transaction data entry is a transaction messageformatted based on one or more standards, and the specific digital tokennumber or specific transaction account number included in thetransaction data entry is stored in a data element included in thetransaction message configured to store a primary account number. 17.The system of claim 16, wherein the one or more standards includes theISO 8583 standard.
 18. The system of claim 15, wherein the queryingmodule of the processing server is further configured to execute a queryon the token profile database to identify a specific token profile wherethe included digital token number corresponds to the specific digitaltoken number included in the received transaction data entry if thereceived transaction data entry includes a specific digital tokennumber, and the associated specific transaction account numbercorresponds to the associated transaction account number included in theidentified specific token profile.
 19. The system of claim 15, whereinthe at least one token profile associated with the third party entityincluded in the identified plurality of related token profiles includescommunication data associated with the third party entity, andidentifying the third party entity includes executing, by the queryingmodule of the processing server, a query on the identified plurality ofrelated token profiles to identify the at least one token profileincluding communication data associated with the third party entity. 20.The system of claim 15, wherein the computing device data includes atleast one of: make, manufacturer, model, form factor, architecture,type, and geographic location.